Skip to content

fix: use mistral-vibe-cli-latest as default model for Mistral AI#1188

Open
currentsuspect wants to merge 3 commits into
Gitlawb:mainfrom
currentsuspect:fix/mistral-default-model
Open

fix: use mistral-vibe-cli-latest as default model for Mistral AI#1188
currentsuspect wants to merge 3 commits into
Gitlawb:mainfrom
currentsuspect:fix/mistral-default-model

Conversation

@currentsuspect
Copy link
Copy Markdown

Summary

Changes the default model for the Mistral AI gateway from devstral-latest to mistral-vibe-cli-latest. The vibe model has better rate limits and is more current.

devstral-latest is kept in the catalog as an available alternative.

Changes

  • mistral.ts: Updated defaultModel from 'devstral-latest' to 'mistral-vibe-cli-latest'
  • mistral.ts: Added mistral-vibe-cli-latest to the static model catalog

Verification

  • Tested mistral-vibe-cli-latest against https://api.mistral.ai/v1/chat/completions — responds correctly
  • bun test src/services/api/openaiShim.test.ts — 95 pass
  • bun run build — clean

Closes #1181

🤖 Generated with OpenClaude

Copilot AI review requested due to automatic review settings May 15, 2026 19:16
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Switches the Mistral AI gateway's default model from devstral-latest to mistral-vibe-cli-latest (which has higher rate limits per the linked issue) and adds the new model to the static catalog while keeping devstral-latest available.

Changes:

  • Update defaultModel in the Mistral gateway descriptor to mistral-vibe-cli-latest.
  • Add a mistral-vibe-cli catalog entry pointing at mistral-vibe-cli-latest with a matching modelDescriptorId.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

catalog: {
source: 'static',
models: [
{ id: 'mistral-vibe-cli', apiName: 'mistral-vibe-cli-latest', label: 'Vibe CLI Latest', modelDescriptorId: 'mistral-vibe-cli-latest' },
@Vasanthdev2004
Copy link
Copy Markdown
Collaborator

Blockers

None.

Non-Blocking

None.

Looks Good

  • Changes default model from devstral-latest to mistral-vibe-cli-latest
  • Adds new model to brand, gateway, and model catalogs
  • devstral-latest kept as available alternative
  • 4 additions, 1 deletion — minimal change
  • 95 tests passing

Verdict: Approve — clean default model update.

Vasanthdev2004
Vasanthdev2004 previously approved these changes May 16, 2026
Copy link
Copy Markdown
Collaborator

@Vasanthdev2004 Vasanthdev2004 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean default model update.

gnanam1990
gnanam1990 previously approved these changes May 16, 2026
Copy link
Copy Markdown
Collaborator

@gnanam1990 gnanam1990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving — thanks, this is clean and well-scoped. 🎉

Resolves #1181, and the descriptor/brand/catalog entries are now consistent so the integrations registry validation passes. The Copilot-flagged missing-descriptor issue was addressed in your follow-up commit. Good detail: defaultModel only affects newly-created Mistral profiles, so existing users keep their stored model, and devstral-latest stays available in the catalog as an alternative. Nicely done.

Copy link
Copy Markdown
Collaborator

@jatmn jatmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Findings

  • [P1] Update the Mistral profile defaults used by /provider
    src/utils/providerProfile.ts:47
    The descriptor default now points at mistral-vibe-cli-latest, but the interactive Mistral setup path still uses DEFAULT_MISTRAL_MODEL, which remains devstral-latest. ProviderWizard passes that value into the Mistral model prompt, and leaving the prompt blank saves step.defaultModel, so the exact workflow from #1181 still creates a Mistral profile on devstral-latest. Please update the runtime/profile default path as well, and cover it with the existing provider/profile tests so the descriptor and setup defaults cannot drift again.

@gnanam1990
Copy link
Copy Markdown
Collaborator

Thanks for chasing this down, and apologies for the earlier approval from my side — it predated the issue below and is superseded by @jatmn's review, which is correct.

Re-checking against the code: the PR updates only the gateway descriptor's defaultModel, but the user-facing default still resolves to devstral-latest through DEFAULT_MISTRAL_MODEL (providerProfile.ts:47), which is what the /provider wizard and buildMistralProfileEnv actually consume. So the workflow in #1181 — selecting Mistral in the wizard and getting mistral-vibe-cli-latest — isn't fixed yet by this change alone.

Updating DEFAULT_MISTRAL_MODEL to match, plus a small test pinning the wizard/profile default to the descriptor default so the two can't drift again, should close this out cleanly. Thanks again for the contribution — looking forward to the follow-up.

Copilot AI review requested due to automatic review settings May 17, 2026 07:49
@currentsuspect currentsuspect dismissed stale reviews from gnanam1990 and Vasanthdev2004 via 6369de1 May 17, 2026 07:49
currentsuspect and others added 3 commits May 17, 2026 10:49
Change the default model from devstral-latest to mistral-vibe-cli-latest
which has better rate limits and is more current. Keep devstral-latest
in the catalog as an available alternative.

Closes Gitlawb#1181

Co-Authored-By: OpenClaude (mimo-v2.5-pro) <[email protected]>
The catalog entry referenced a modelDescriptorId that had no matching
descriptor in src/integrations/models/mistral.ts, causing integration
test failures (gateway modelDescriptorId references have model metadata,
registry is valid after loading all descriptors).

Co-Authored-By: OpenClaude (mimo-v2.5-pro) <[email protected]>
The /provider interactive setup still defaulted to devstral-latest via
DEFAULT_MISTRAL_MODEL, even though the gateway descriptor points at
mistral-vibe-cli-latest. Update the constant and add a test that
asserts DEFAULT_MISTRAL_MODEL matches the gateway defaultModel to
prevent future drift.

Co-Authored-By: OpenClaude (mimo-v2.5-pro) <[email protected]>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use mistral-vibe-cli-latest as default model for Mistral AI

5 participants